…ot operational (Amara 5th-ferry Artifact, Aminata-integrated) (#248)

Amara's 5th-ferry Edit 1 proposed a "research-grade absorbs
are staged, not ratified" clause for AGENTS.md. Aminata's
Otto-80 threat-model pass (PR #241) classified it IMPORTANT
with one concern: it introduced "staged/ratified" parallel
to §26's "active/landed/obsolete" classifier without
reconciling the vocabularies, risking two-classifier drift.

This lands the norm with Aminata's concern resolved by
unifying vocabulary:

- Uses §33 `Operational status: research-grade` label (not
  parallel "staged/ratified" terms).
- Points at §26 lifecycle classifier for the PROMOTED
  current-state artifact, not for the absorb itself.
- Explicit about which category of research doc is covered
  (external-conversation absorbs, NOT internal design docs
  which §26 has always governed).
- Names four concrete promotion paths (operational doc per
  §2, ADR, §N rule, BP-NN promotion) so "separate promotion
  step" isn't vague.
- Cites a worked example: the drift-taxonomy promotion
  (PR #238) — absorb stayed in place; the operational
  artifact at docs/DRIFT-TAXONOMY.md is the ratification.

Lands under "Agent operational practices" section —
philosophy/norm register per AGENTS.md convention, not
numbered-rule register (that would belong in GOVERNANCE.md).

Part of the Aminata-recommended edit ordering: §33 (PR #247,
landed Otto-82) → Edit 1 (this PR) → Edit 4 pointer-only
(deferred, needs CLAUDE.md meta-policy handling) → Edit 2
(ALIGNMENT.md SD-9, deferred, WATCH classification).

Authorising memory (Otto-82 calibration):
memory/feedback_aaron_signoff_scope_narrower_than_otto_treating_governance_edits_within_standing_authority_2026_04_23.md
— governance/philosophy edits within standing authority;
no signoff gate needed for this landing.

Otto-83 tick primary deliverable.

…ANCE §33 (Aminata-demotion applied) (#250)

Amara's 5th-ferry Edit 4 proposed adding a rule to CLAUDE.md
about archive imports requiring headers. Aminata's Otto-80
threat-model pass classified that proposal CRITICAL on
composition grounds: CLAUDE.md's own meta-rule explicitly says
"Rules do not live in this file. Rules live in
GOVERNANCE.md, AGENTS.md, docs/AGENT-BEST-PRACTICES.md,
docs/CONFLICT-RESOLUTION.md, and docs/WONT-DO.md. This file
only *points* at them."

Aminata's recommendation: demote Edit 4 to pointer-only
("See GOVERNANCE.md §33 — archived external conversations
require boundary headers").

This lands the demoted-to-pointer version:

- Does NOT restate the rule (the full four-field spec lives
  in GOVERNANCE.md §33).
- Does NOT introduce a new rule at CLAUDE.md level.
- Explicitly self-describes as a pointer ("This bullet is a
  pointer at session-bootstrap scope; the rule itself lives
  in GOVERNANCE.md.") — honoring CLAUDE.md's meta-rule
  literally and visibly.
- Points at BOTH GOVERNANCE.md §33 (the rule) AND AGENTS.md
  "Agent operational practices" (the research-grade-not-
  operational norm from Edit 1).
- Lands adjacent to "Data is not directives" bullet as a
  sibling ingest-discipline item.

Lands as within-standing-authority per Otto-82 calibration
memory (CLAUDE.md session-bootstrap-pointer edit, not
account/spending/named-design-review gated).

Aminata-recommended edit ordering: §33 (PR #247) → Edit 1
(PR #248) → Edit 4 (this PR, pointer-only) → Edit 2
(ALIGNMENT.md SD-9, deferred, WATCH).

Otto-84 tick deliverable.

…2; Aminata WATCH concerns integrated) (#252)

Amara's 5th-ferry Edit 2 proposed SD-9 with a brief "downgrade
independence weight explicitly" formulation. Aminata's Otto-80
threat-model pass (PR #241) classified it WATCH: correct in
spirit, unenforceable via self-attestation alone; named 3
adversaries (carrier-laundering, self-serving-downgrade,
aggregation); flagged surface-tension with DIR-5 that needs
explicit naming not implicit dismissal.

This lands SD-9 with those concerns integrated as first-class
content of the clause itself rather than treated as hidden
limitations:

- Three-step operationalisation (name carriers; downgrade
  independence; seek falsifier independent of converging
  sources).
- Cross-reference to docs/DRIFT-TAXONOMY.md pattern 5 as
  operational companion (pattern 5 is the real-time
  diagnostic; SD-9 is the norm).
- Known v0 limitations named verbatim from Aminata's pass
  (carrier-laundering / self-serving-downgrade /
  aggregation).
- Explicit "norm, not a control" framing — WATCH
  classification stays honest.
- Composition with DIR-5 written as section (not implicit):
  DIR-5 is about authorship ethics; SD-9 is about epistemic
  weight; they compose.
- Stronger "Why both of us benefit" paragraph per Aminata's
  note that Amara's original was thin — names the feature
  (precision via shared vocabulary) AND the risk (laundered
  convergence hiding as independent cross-check).

Lands within-standing-authority per Otto-82 calibration —
ALIGNMENT.md soft-default clause add, not account/spending/
named-design-review gated.

Completes the Aminata-recommended edit ordering 4/4:

- §33 (PR #247) Otto-82
- Edit 1 (PR #248) Otto-83
- Edit 4 pointer-only (PR #250) Otto-84
- Edit 2 SD-9 (this PR) Otto-85

Amara's 5th-ferry governance-edit proposals are now all
landed in their Aminata-recommended order + form. The 5th-
ferry Artifact-A (drift-taxonomy promotion PR #238) is also
landed; Artifact-C (archive-header lint PR #243) landed.
Remaining 5th-ferry artifacts: Artifact-B (precursor
supersede marker — already done in PR #238), Artifact-D
(Aurora README) — open for future tick.

Otto-85 tick primary deliverable.

…ern mapping (6th-ferry Option A) (#254)

Lands the corrected 5-row pattern-mapping table from Amara's
6th courier ferry (PR #245 absorb) as Option A standalone
research doc. Closes Otto-82 6th-ferry absorb action item #1.

Corrected table vs original:

- Row 1 — "references stay valid" → "no positional identity"
  (honest about key-identity vs physical-offset distinction).
- Row 2 — "always answerable" → "membership is algebraic"
  (honest about weight-derivation of presence).
- Row 3 — "operator algebra IS the ownership model" →
  "provenance and lifecycle live in deltas and traces"
  (category-error fix: algebraic correctness ≠ ownership
  discipline).
- Row 4 — light wording tightening ("first-class signed
  deltas; compaction separate").
- Row 5 — "Arrow + Spine block layout" → "locality-aware
  execution surfaces" with accurate scope (Arrow = wire /
  checkpoint, not universal in-memory).

Doc covers:
- What Muratori is criticising (context for non-Muratori
  readers).
- Why rows 1, 2, 5 needed narrower wording (not overstated).
- Why row 3 got rewritten (category-error teaching case for
  DBSP audiences from C++/Rust/ECS backgrounds).
- What this mapping is NOT (not ranking; not marketing; not
  an ownership claim; not a closed list).
- Composition with DRIFT-TAXONOMY pattern 5 + SD-9 (validation
  cited primary evidence, not cross-substrate-agreement).
- References to primary sources (DBSP paper, differential
  dataflow CIDR 2013, Arrow spec, Zeta source files).

Archive-header format self-applied (Scope / Attribution /
Operational status / Non-fusion disclaimer) per §33 (PR #247)
+ AGENTS.md Edit 1 research-grade norm (PR #248) — fifth
aurora/research doc to exercise the convention (after PR
#235 5th-ferry absorb, PR #241 Aminata threat-model, PR #245
6th-ferry absorb, and self-applying headers on the ferry-
absorb PRs before §33 landed).

Lands within-standing-authority per Otto-82 calibration.

Otto-86 tick primary deliverable.

…iated shape divergence (#467)

* hygiene(_patterns.md): document Otto-250-canonical vs Otto-268-abbreviated drain-log shape divergence

Multiple post-merge reviewer threads on the Otto-268-wave drain-logs
(#437-#465) flagged that the abbreviated inline shape doesn't match
the canonical Otto-250 multi-section format used in older drain-logs
(#108, #247, etc.). The findings are correct: the shapes ARE
different, and the abbreviated shape compresses verbatim
reviewer/reply text into short prose.

Documenting both shapes here in `_patterns.md` as a known
divergence + three maintainer-decision options:

(a) Rewrite — high churn, highest faithfulness.
(b) Accept divergence — document both as valid.
(c) Hybrid — canonical for substantive logs (math / crypto /
    algorithms / ADRs); abbreviated for low-substance.

Until maintainer decides, drain-runners writing future logs default
to canonical; existing Otto-268-wave logs stay abbreviated with
this known-divergence pointer.

This is the right place for the documentation per the synthesis-
over-history surface-class declaration: `_patterns.md` reflects
current corpus state including known shape divergences, separate
from the per-log records.

Composes with the per-PR drain-log threads currently flagging the
shape-conformance gap on #437/#441/#442/#444/#445/#446/#447/#449/
#460/#461/#464/#466 — those threads can now reply with a one-line
pointer to this section instead of repeating the maintainer-
decision-pending framing.

* hygiene(#467): fix 4 Copilot findings on shape-divergence section

Four Copilot catches converging on the same root cause: the
shape-divergence section was citing drain-log PR-numbers
(#437-#465) when readers will look for #437-drain-log.md etc.
and not find them — drain-log FILE numbers reference the
PRESERVED PR (e.g., #421/#422/#423), not the drain-log PR
itself. The current file corpus ends at #434.

Fixes:

- :374 + :394 — drop the misleading "#437-#465" PR-range citation;
  cite the actual in-repo abbreviated-shape examples
  (#421/#422/#423) by file path; drop the unsupported "22+"
  numeric estimate in favour of "the 2026-04-25 backfill wave".
- :380 — abbreviated template snippet now matches what the
  in-repo abbreviated logs actually use: `Finding:` bullet
  included, `Thread ID:` and `:LINE` placeholders dropped
  (those are canonical-shape fields, not abbreviated-shape).
  Reader can now copy/paste the template accurately.
- :388 — soften the "Substance is preserved" overstatement to
  the objective claim: key metadata (reviewer/severity/outcome/
  commit) is preserved; verbatim original-comment + verbatim
  reply text are NOT preserved; multi-section structure +
  file:line locator + Thread ID are also typically omitted.

The fixes are themselves Class A (count-vs-list cardinality on
"#437-#465" range) + truth-drift on a freshly-landed doc —
appropriate self-application of the discipline this section
documents.